Skip to content

docs: design the review-fix-loop skill - #91

Merged
shaug merged 1 commit into
mainfrom
scott/review-fix-loop-design
Jul 30, 2026
Merged

docs: design the review-fix-loop skill#91
shaug merged 1 commit into
mainfrom
scott/review-fix-loop-design

Conversation

@shaug

@shaug shaug commented Jul 30, 2026

Copy link
Copy Markdown
Owner

TL;DR

Defines the future review-fix-loop skill and its integration boundaries so implementation tickets have a stable architectural reference.

Summary

  • Defines a mandatory, invocation-budgeted review and remediation loop around the complete repository-owned review suite.
  • Makes fresh read-only reviewer subagents the default, with explicit capability isolation and a recorded in-agent override path.
  • Establishes candidate ownership, crash recovery, terminal-state, publication, and acceptance-reconciliation contracts.
  • Keeps fixes local until convergence, except for narrowly authorized update_pr mechanisms that demonstrably require an origin-visible head.
  • Specifies the migration impact on implement-ticket, babysit-pr, review-code-change, its lenses, implement-epic, and carve-changesets.

Design decisions

  • No zero-cycle or review-only mode.
  • One fix-cycle budget per invocation.
  • No focused or custom mutating review profiles in the initial skill.
  • No implicit in-agent review fallback.
  • No implicit remote publication authority.

Validation

  • just format
  • just lint
  • just test
  • Fresh exact-head aggregate review: clean

## Summary

- Add the converged design contract for the standalone review/fix loop
- Define reviewer isolation, bounded convergence, ownership handoff, publication,
  recovery, and caller integration requirements
- Record the design in the repository changelog

## Why

- Give future implementation tickets a stable, reviewable architectural
  reference
- Separate reusable review/fix behavior from larger ticket and PR workflows
@shaug
shaug merged commit 06538e5 into main Jul 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant